-
-
Notifications
You must be signed in to change notification settings - Fork 875
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Remove ParseUI
#1783
feat: Remove ParseUI
#1783
Conversation
Thanks for opening this pull request!
|
@mtrezza Codecov is broken |
Have the Privacy Manifests been added to the project yet? Worth including them here with this PR or best to do that in a separate PR? |
@JohnCaccavale They haven't been added. If they do it will be separate PR. Can you open an issue for it? I need to do some research on it. |
🎉 This change has been released in version 4.0.0 |
New Pull Request Checklist
Issue Description
Building a UI has become a lot easier over the years, especially with SwiftUI; ParseUI today looks like an obsolete convenience that could be dropped from the Parse SDK. This is a breaking change.
Closes: #1760
Closes: #1729
Closes: #1493
Closes: #1406
Closes: #1517
Approach
Remove ParseUI.
TODOs before merging